PROFINET IO-Device V4

Version V4.5.0.7

Changes:

• PSPNSV4-1208: update to LWIP V4.2.0.8
• PSPNSV4-1207: Upgrade rcX operating system to V2.1.16.1
• PSPNSV4-1202: update to PN Core V1.9.0.15

Bugs:

• PSPNSV4-1206: [System Redundancy] Submodule ownership not handled properly

Version V4.5.0.6

Changes:

• PSPNSV4-1200: Upgrade LwIP to V4.2.0.6
• PSPNSV4-1196: Upgrade Profinet Device Interface to V1.1.0.4
• PSPNSV4-1194: Upgrade Profinet Core to V1.9.0.14

Bugs:

• PSPNSV4-1201: Single cyclic frames might be missing during IRT operation
• PSPNSV4-1198: Read Implicit handling for Target ARUUID has some minor issues
• PSPNSV4-1197: Padding sometimes not set to zero in negative read implicit response
• PSPNSV4-1195: Unexpected behavior on APDU status change service
• PSPNSV4-1191: wrong value for hAlarmHandle returned in PNS_IF_SEND_ALARM_CNF

Version V4.5.0.5

Changes:

• PSPNSV4-1187: Upgrade Profinet Core to V1.9.0.12
• PSPNSV4-1185: RUN flag is not cleared, when evaluation time of limited firmware expires

Bugs:

• PSPNSV4-1184: inconsistent NameOfStation reported in different access ways in case of Non-Profinet neighbor

Version V4.5.0.4

Changes:

• PSPNSV4-1178: Upgrade Profinet Core to V1.9.0.11

Bugs:

• PSPNSV4-1179: Application Ready sometimes not send
• PSPNSV4-1175: Sometimes IRT frames missing

Version V4.5.0.3

Changes:

• PSPNSV4-1167: Upgrade Profinet Core to V1.9.0.10

Bugs:

• PSPNSV4-1166: AR state Indications sometimes not generated

Version V4.5.0.2

Changes:

• PSPNSV4-1165: Upgrade Profinet Core to V1.9.0.9

Bugs:

• PSPNSV4-1164: Network communication stops operation after a while if NDIS API is activated

Version V4.5.0.1

Changes:

• PSPNSV4-1160: SystemRedundancy Firmwares: adjust number of AR ressources in taglist
• PSPNSV4-1147: Upgrade Profinet Device Interface to V1.1.0.3

Bugs:

• PSPNSV4-1151: GSDML file for NRP51-RE-IO is missing
• PSPNSV4-1150: Upgrade Profinet Core to V1.9.0.6

Version V4.5.0.0

New Features:

• PSPNSV4-1086: Add support for process alarm with User Structure Identifier 0x8320
• PSPNSV4-908: Feature: Add support to some netX firmware targets as standard Ethernet interface (NDIS)
• PSPNSV4-905: Feature: Add support for SFDP (in case compatilbe 2nd StageBootloader exists)
• PSPNSV4-849: Feature: Add API for application to modify some version number related values in case of database configuration
• PSPNSV4-848: Feature: Allow usage of more than Assets in AssetManagment
• PSPNSV4-847: Feature: Add API for application to modify some version Device identity values in case of database configuration
• PSPNSV4-787: Feature: Add support for Sycon.net database with profile submodules (API != 0)
• PSPNSV4-781: Support Set OEM Parameter Type 9
• PSPNSV4-770: Feature: Add possibility to copy the Profinet cycle counter to DPM (Set OEM Prm Type 6)

Changes:

• PSPNSV4-1144: Upgrade Hilscher Firmware Definitions to 20190731-00
• PSPNSV4-1142: Upgrade Profinet Device Interface to V1.1.0.2
• PSPNSV4-1135: Upgrade Profinet Core to V1.9.0.2
• PSPNSV4-1123: Upgrade Profinet Core to V1.9.0.1
• PSPNSV4-1107: drop support for netident protocol
• PSPNSV4-1106: Upgrade Hilscher Firmware Definitions to 20190520-00
• PSPNSV4-1105: Upgrade firmware components to most recent versions
• PSPNSV4-1104: Upgrade lwIP based IP stack to V4.1.4.0
• PSPNSV4-1103: Upgrade rcX operating system to V2.1.14.1
• PSPNSV4-1095: Upgrade Profinet Device Interface to V1.1.0.0
• PSPNSV4-1055: Wrong encoding of SubmoduleState.AddInfo
• PSPNSV4-1054: Upgrade Profinet Core to V1.9.0.0
• PSPNSV4-962: Upgrade device description files to GSDML V2.34
• PSPNSV4-947: Update WAF build scripts to V1.9.0.0
• PSPNSV4-882: Do not remove static ARP entry when another AR exists
• PSPNSV4-872: do not enforce PPM to send a cyclic frame prior sending ConnectResponse
• PSPNSV4-766: update to newest Hilscher definitions and Generic AP Task
• PSPNSV4-639: allow newly defined Profile specific records to be used by applications

Bugs:

• PSPNSV4-1140: Overlapping of IRT Cycle Counter Offset with DPM Input offsets not detected.
• PSPNSV4-1138: [GSDML]: missing dash in version information of DAP V4.5
• PSPNSV4-1118: Firmware crash or malfunctioning when handling multiple services related to remanent data in a short time
• PSPNSV4-1117: Wrong ModuleDiffBlock entry when a expected submodule not available
• PSPNSV4-1116: Missing configuration database file is not shown in Communication error
• PSPNSV4-1115: Unexpected IRT related diagnosis reported
• PSPNSV4-1111: Invalid Module Diff Block and Check Indications with unsorted Expected submodule blocks
• PSPNSV4-1102: [netX52]: firmware may crash when FSU is used with fix Ethernet port settings and firmware handles remanent data
• PSPNSV4-1097: Wrong coding of AM_DeviceIdentification in asset management block
• PSPNSV4-1088: Last confirmation packet of a fragmented request has sequence set to zero
• PSPNSV4-1085: Remanent data not deleted on Delete Config service
• PSPNSV4-1084: Communicating Bit cleared to early
• PSPNSV4-979: Profinet Netload certification tests fail
• PSPNSV4-966: LLDP frame with invalid RTC3 Port Status encoding sent
• PSPNSV4-964: Legacy startup sometimes aborted
• PSPNSV4-944: IRT communication is instable in large networks in case different cycle times are used
• PSPNSV4-942: Invalid/wrong plug submodule alarm sent
• PSPNSV4-936: PDRealData read response may contain unexpected PeerPortName in case of Non-Profinet neighbor
• PSPNSV4-927: Double or missing check indications on connect when reconfiguring
• PSPNSV4-911: IRT communication can not be established in large networks
• PSPNSV4-910: unexpected Sync offset in longer lines in case of IRT
• PSPNSV4-902: Unexpected behavior of Check Services
• PSPNSV4-901: Unexpected Connect Request Done Indication when reconfiguring
• PSPNSV4-898: Wrong behavior in case IO Controller does not acknowledge an alarm
• PSPNSV4-897: Service PNS_IF_UPDATE_PE_ENTITY_REQ is not rejected when used for a none-PE submodule
• PSPNSV4-894: TED conformance check failes due missing SNMP Mib entries in case of None-Profinet neighbor
• PSPNSV4-891: Connection abort in case of negative alarm confirmation
• PSPNSV4-888: Firmware may crash when loading a database
• PSPNSV4-887: No Parameter End Response when submodule plugged immediately after establishing connection
• PSPNSV4-885: Establishing an AR after high network load not possible in some cases
• PSPNSV4-881: Sometimes change of NameOfStation and IP address not indicated
• PSPNSV4-880: Submodule ownership not released under certain conditions
• PSPNSV4-879: DCP ResetToFactory does not reset all fields
• PSPNSV4-862: Memory leak when bus is switched to on
• PSPNSV4-861: Endpoint mapper annotation not set on very first BusOn transition
• PSPNSV4-857: PDRealData object misses PDPortStatistic block of interface submodule
• PSPNSV4-856: Unexpected Return of Submodule Alarms after Application Ready in rare cases
• PSPNSV4-842: in case a SetConfiguration packet contains more submodules than allowed in taglist the packet is returned with unexpected error code
• PSPNSV4-841: Packet Socket API crash on UDP traffic
• PSPNSV4-831: too much data delivered in case of partial read for ModuleDiffBlock
• PSPNSV4-829: Wrong error code in case of reconnect
• PSPNSV4-821: Wrong CMI/CPM connection monitoring in for legacy startup
• PSPNSV4-805: Memory leak when using profile specific generic diagnosis
• PSPNSV4-710: SubmoduleState.AddInfo is not set correctly

Version V4.4.10.0

Changes:

• PSPNSV4-1144: Upgrade Hilscher Firmware Definitions to 20190731-00
• PSPNSV4-1142: Upgrade Profinet Device Interface to V1.1.0.2
• PSPNSV4-1135: Upgrade Profinet Core to V1.9.0.2

Bugs:

• PSPNSV4-1140: Overlapping of IRT Cycle Counter Offset with DPM Input offsets not detected.
• PSPNSV4-1138: [GSDML]: missing dash in version information of DAP V4.5

Version V4.4.9.0

Changes:

• PSPNSV4-1123: Upgrade Profinet Core to V1.9.0.1

Bugs:

• PSPNSV4-1118: Firmware crash or malfunctioning when handling multiple services related to remanent data in a short time

Version V4.4.8.0

New Features:

• PSPNSV4-1086: Add support for process alarm with User Structure Identifier 0x8320

Changes:

• PSPNSV4-1107: drop support for netident protocol
• PSPNSV4-1106: Upgrade Hilscher Firmware Definitions to 20190520-00
• PSPNSV4-1105: Upgrade firmware components to most recent versions
• PSPNSV4-1104: Upgrade lwIP based IP stack to V4.1.4.0
• PSPNSV4-1103: Upgrade rcX operating system to V2.1.14.1
• PSPNSV4-1095: Upgrade Profinet Device Interface to V1.1.0.0
• PSPNSV4-1055: Wrong encoding of SubmoduleState.AddInfo
• PSPNSV4-1054: Upgrade Profinet Core to V1.9.0.0

Bugs:

• PSPNSV4-1117: Wrong ModuleDiffBlock entry when a expected submodule not available
• PSPNSV4-1116: Missing configuration database file is not shown in Communication error
• PSPNSV4-1115: Unexpected IRT related diagnosis reported
• PSPNSV4-1111: Invalid Module Diff Block and Check Indications with unsorted Expected submodule blocks
• PSPNSV4-1102: [netX52]: firmware may crash when FSU is used with fix Ethernet port settings and firmware handles remanent data
• PSPNSV4-1097: Wrong coding of AM_DeviceIdentification in asset management block
• PSPNSV4-1088: Last confirmation packet of a fragmented request has sequence set to zero
• PSPNSV4-1085: Remanent data not deleted on Delete Config service
• PSPNSV4-1084: Communicating Bit cleared to early
• PSPNSV4-944: IRT communication is instable in large networks in case different cycle times are used
• PSPNSV4-942: Invalid/wrong plug submodule alarm sent

Version V4.4.7.0

New Features:

• PSPNSV4-849: Feature: Add API for application to modify some version number related values in case of database configuration

Changes:

• PSPNSV4-1021: Upgrade Profinet Core to V1.7.6.0
• PSPNSV4-1017: Upgrade Generic AP Task to V1.0.0.1

Bugs:

• PSPNSV4-1051: [GCI-Adapter] Mismatch between Communication Error, LED state and Link Status
• PSPNSV4-1040: [netX90/netX4000] Device loses permanently stored IP address
• PSPNSV4-1035: [netX90/4000] wrong error code used when connection to IO Controller is aborted due to DPM watchdog error
• PSPNSV4-1034: [netX90/4000] Profienergy ASE is active by default
• PSPNSV4-1014: [netX90/netX4000] Wrong watchdog time after set configuration service
• PSPNSV4-1011: [netX90/netX4000] HIL_GET_TRIGGER_TYPE_REQ returns unexpected values in case a HIL_SET_TRIGGER_TYPE_REQ was rejected upfront
• PSPNSV4-1009: [netX90/netX4000] PNS_IF_PARAMET_SPEEDUP_SUPPORTED_IND is not generated
• PSPNSV4-1008: [GCI-adapter]: PNS_IF_GET_PARAM_REQ is rejected with unknown command
• PSPNSV4-1005: [netX90/netX4000] DPM Mailbox freeze and device not reachable on network on high network load
• PSPNSV4-989: [GCI-adapter]: some PNS_IF_SET_OEM_PARAMETER_REQ parameter types are rejected with invalid parameter
• PSPNSV4-987: [GCI-adapter]: PNS_IF_SEND_PROCESS_ALARM_REQ is rejected with unknown command
• PSPNSV4-979: Profinet Netload certification tests fail

Version V4.4.6.0

New Features:

• PSPNSV4-996: [netX90, netX4000]: extend taglist by new tag to define who is responsible for handling remanent data

Bugs:

• PSPNSV4-1002: [netX90]: Use case A firmware does not offer WebIf API
• PSPNSV4-1001: [GCI-adapter]: adapt DPM Channel 1 name to new definition
• PSPNSV4-1000: [GCI-adapter]: Return Of Submodule service not supported
• PSPNSV4-999: Application CPU not started on netX90
• PSPNSV4-993: [GCI-adapter]: PNS_IF_SET_SUBM_STATE_REQ not implemented
• PSPNSV4-991: [GCI-adapter]: PNS_IF_ABORT_CONNECTION_REQ not implemented
• PSPNSV4-988: [GCI-adapter]: HIL_LOCK_UNLOCK_CONFIG_REQ not implemented
• PSPNSV4-986: [GCI-adapter]: PNS_IF_GET_STATION_NAME_REQ not implemented

Version V4.4.5.0

New Features:

• PSPNSV4-908: Feature: Add support to some netX firmware targets as standard Ethernet interface (NDIS)
• PSPNSV4-770: Feature: Add possibility to copy the Profinet cycle counter to DPM (Set OEM Prm Type 6)

Changes:

• PSPNSV4-984: Generate netX90 firmware for usecase "C"
• PSPNSV4-982: [GCI-adapter]: Introduce PHY enable timeout in case of unconfigured protocol stack
• PSPNSV4-962: Upgrade device description files to GSDML V2.34
• PSPNSV4-947: Update WAF build scripts to V1.9.0.0
• PSPNSV4-940: Update Profinet Core to V1.7.5.0

Bugs:

• PSPNSV4-976: [netX90]: unexpected high cable delay values meassured by PTCP
• PSPNSV4-974: [GCI-adapter]: Bus State Change not working
• PSPNSV4-973: [GCI-adapter]: reading I&M0 data returns wrong data after first configuration cycle
• PSPNSV4-966: LLDP frame with invalid RTC3 Port Status encoding sent
• PSPNSV4-964: Legacy startup sometimes aborted
• PSPNSV4-936: PDRealData read response may contain unexpected PeerPortName in case of Non-Profinet neighbor
• PSPNSV4-911: IRT communication can not be established in large networks
• PSPNSV4-910: unexpected Sync offset in longer lines in case of IRT

Version V4.4.4.0

New Features:

• PSPNSV4-934: Implement Set Trigger Type service
• PSPNSV4-929: Support Database configuration for netX90/netX4000 firmwares
• PSPNSV4-915: Integrate eCos Middleware V0.0.0.1
• PSPNSV4-905: Feature: Add support for SFDP (in case compatilbe 2nd StageBootloader exists)
• PSPNSV4-781: Support Set OEM Parameter Type 9

Changes:

• PSPNSV4-939: Update rcX to V2.1.13.0
• PSPNSV4-938: Update component rcX Toolbox to V1.6.0.0
• PSPNSV4-928: Integrate Config Manager V1.2.2.0
• PSPNSV4-925: Upgrade NetX Toolbox to V1.2.5.0
• PSPNSV4-924: Integrate Webserver V0.0.1.0 for netX90/netX4000
• PSPNSV4-923: Upgrade lwIP to V4.1.2.0
• PSPNSV4-920: Upgrade Storage Library (eCos) to V0.0.0.1
• PSPNSV4-919: Upgrade HAL Toolbox to V1.2.3.0
• PSPNSV4-918: Upgrade netX Diagnostics (eCos) to V0.0.0.4
• PSPNSV4-917: Upgrade Generic AP-Task to V0.0.5.0
• PSPNSV4-916: Upgrade PS Toolbox to V1.3.5.0
• PSPNSV4-914: Upgrade eCos to V0.0.0.6
• PSPNSV4-895: Update component LLDP to V5.2.0.3
• PSPNSV4-890: Update component Profinet Core to V1.7.4.0
• PSPNSV4-639: allow newly defined Profile specific records to be used by applications

Bugs:

• PSPNSV4-927: Double or missing check indications on connect when reconfiguring
• PSPNSV4-902: Unexpected behavior of Check Services
• PSPNSV4-901: Unexpected Connect Request Done Indication when reconfiguring
• PSPNSV4-898: Wrong behavior in case IO Controller does not acknowledge an alarm
• PSPNSV4-897: Service PNS_IF_UPDATE_PE_ENTITY_REQ is not rejected when used for a none-PE submodule
• PSPNSV4-894: TED conformance check failes due missing SNMP Mib entries in case of None-Profinet neighbor
• PSPNSV4-891: Connection abort in case of negative alarm confirmation
• PSPNSV4-856: Unexpected Return of Submodule Alarms after Application Ready in rare cases
• PSPNSV4-821: Wrong CMI/CPM connection monitoring in for legacy startup
• PSPNSV4-710: SubmoduleState.AddInfo is not set correctly

Version V4.4.3.0

New Features:

• PSPNSV4-848: Feature: Allow usage of more than Assets in AssetManagment
• PSPNSV4-847: Feature: Add API for application to modify some version Device identity values in case of database configuration
• PSPNSV4-787: Feature: Add support for Sycon.net database with profile submodules (API != 0)

Changes:

• PSPNSV4-884: Update DCE RPC to V5.3.0.3
• PSPNSV4-882: Do not remove static ARP entry when another AR exists
• PSPNSV4-878: Update Waf buildsystem to V1.8.16.0
• PSPNSV4-874: Update component Profinet Core to V1.7.3.0
• PSPNSV4-872: do not enforce PPM to send a cyclic frame prior sending ConnectResponse

Bugs:

• PSPNSV4-888: Firmware may crash when loading a database
• PSPNSV4-887: No Parameter End Response when submodule plugged immediately after establishing connection
• PSPNSV4-885: Establishing an AR after high network load not possible in some cases
• PSPNSV4-881: Sometimes change of NameOfStation and IP address not indicated
• PSPNSV4-880: Submodule ownership not released under certain conditions
• PSPNSV4-879: DCP ResetToFactory does not reset all fields

Version V4.4.2.0

Changes:

• PSPNSV4-866: Update OSAL to V1.3.0.0
• PSPNSV4-864: Update HAL Toolbox to V1.2.2.0
• PSPNSV4-839: Update lwIP stack to V4.1.1.0

Bugs:

• PSPNSV4-862: Memory leak when bus is switched to on
• PSPNSV4-861: Endpoint mapper annotation not set on very first BusOn transition
• PSPNSV4-857: PDRealData object misses PDPortStatistic block of interface submodule
• PSPNSV4-842: in case a SetConfiguration packet contains more submodules than allowed in taglist the packet is returned with unexpected error code
• PSPNSV4-841: Packet Socket API crash on UDP traffic
• PSPNSV4-831: too much data delivered in case of partial read for ModuleDiffBlock
• PSPNSV4-829: Wrong error code in case of reconnect
• PSPNSV4-805: Memory leak when using profile specific generic diagnosis

Version V4.4.1.0

Changes:

• PSPNSV4-830: Integrate GCI interface V0.0.3.0
• PSPNSV4-827: Update external component PS Toolbox to V1.3.3.0
• PSPNSV4-766: update to newest Hilscher definitions and Generic AP Task

Version V4.4.0.9

Changes:

• PSPNSV4-1108: Upgrade Driver Ethernet to V1.5.2.0
• PSPNSV4-1055: Wrong encoding of SubmoduleState.AddInfo
• PSPNSV4-1022: Upgrade Profinet Core to V1.7.0.8

Bugs:

• PSPNSV4-1117: Wrong ModuleDiffBlock entry when a expected submodule not available
• PSPNSV4-1115: Unexpected IRT related diagnosis reported
• PSPNSV4-1111: Invalid Module Diff Block and Check Indications with unsorted Expected submodule blocks
• PSPNSV4-1102: [netX52]: firmware may crash when FSU is used with fix Ethernet port settings and firmware handles remanent data
• PSPNSV4-1101: Buffer overflow when handling user alarm
• PSPNSV4-1097: Wrong coding of AM_DeviceIdentification in asset management block
• PSPNSV4-942: Invalid/wrong plug submodule alarm sent

Version V4.4.0.8

Bugs:

• PSPNSV4-964: Legacy startup sometimes aborted

Version V4.4.0.7

Changes:

• PSPNSV4-943: Update component Profinet Core to V1.7.0.6

Bugs:

• PSPNSV4-936: PDRealData read response may contain unexpected PeerPortName in case of Non-Profinet neighbor
• PSPNSV4-911: IRT communication can not be established in large networks
• PSPNSV4-910: unexpected Sync offset in longer lines in case of IRT
• PSPNSV4-710: SubmoduleState.AddInfo is not set correctly

Version V4.4.0.6

Bugs:

• PSPNSV4-927: Double or missing check indications on connect when reconfiguring

Version V4.4.0.5

Bugs:

• PSPNSV4-902: Unexpected behavior of Check Services
• PSPNSV4-901: Unexpected Connect Request Done Indication when reconfiguring
• PSPNSV4-897: Service PNS_IF_UPDATE_PE_ENTITY_REQ is not rejected when used for a none-PE submodule

Version V4.4.0.4

Changes:

• PSPNSV4-899: Update component Profinet Core to V1.7.0.5

Bugs:

• PSPNSV4-898: Wrong behavior in case IO Controller does not acknowledge an alarm

Version V4.4.0.3

Changes:

• PSPNSV4-895: Update component LLDP to V5.2.0.3
• PSPNSV4-892: Update component Profinet Core to V1.7.0.4

Bugs:

• PSPNSV4-894: TED conformance check failes due missing SNMP Mib entries in case of None-Profinet neighbor
• PSPNSV4-891: Connection abort in case of negative alarm confirmation
• PSPNSV4-856: Unexpected Return of Submodule Alarms after Application Ready in rare cases

Version V4.4.0.2

Changes:

• PSPNSV4-884: Update DCE RPC to V5.3.0.3
• PSPNSV4-882: Do not remove static ARP entry when another AR exists
• PSPNSV4-872: do not enforce PPM to send a cyclic frame prior sending ConnectResponse
• PSPNSV4-844: Update Profinet Core to V1.7.0.3

Bugs:

• PSPNSV4-888: Firmware may crash when loading a database
• PSPNSV4-887: No Parameter End Response when submodule plugged immediately after establishing connection
• PSPNSV4-885: Establishing an AR after high network load not possible in some cases
• PSPNSV4-881: Sometimes change of NameOfStation and IP address not indicated
• PSPNSV4-880: Submodule ownership not released under certain conditions
• PSPNSV4-879: DCP ResetToFactory does not reset all fields
• PSPNSV4-862: Memory leak when bus is switched to on
• PSPNSV4-861: Endpoint mapper annotation not set on very first BusOn transition
• PSPNSV4-857: PDRealData object misses PDPortStatistic block of interface submodule
• PSPNSV4-842: in case a SetConfiguration packet contains more submodules than allowed in taglist the packet is returned with unexpected error code
• PSPNSV4-805: Memory leak when using profile specific generic diagnosis

Version V4.4.0.1

Changes:

• PSPNSV4-838: Update lwIP component to V4.1.0.5

Bugs:

• PSPNSV4-836: Packet Socket API crash on UDP traffic
• PSPNSV4-831: too much data delivered in case of partial read for ModuleDiffBlock
• PSPNSV4-829: Wrong error code in case of reconnect
• PSPNSV4-826: Update PSPNCORE to V1.7.0.2
• PSPNSV4-816: wrong byteorder for AM_Location used in AssetManagment record

Version V4.4.0.0

New Features:

• PSPNSV4-702: Feature: Add API to set some behavior related parameters via mailbox (formerly set via taglist)
• PSPNSV4-670: [NXLFW]: taglist shall allow more detailed modifications regarding memory quantity structure
• PSPNSV4-650: Feature: Add support for newly defined PNS_IF_Get_Parameter ParameterTypes
• PSPNSV4-618: Feature: Add firmware for new products netRAPID51-RE and netRAPID51-RE-IO
• PSPNSV4-617: Feature: Implement API for readout of Ethernet Parameters
• PSPNSV4-616: Feature: Implement API for PROFIenergy ASE
• PSPNSV4-615: Feature: Implement API for UserSpecific Alarms
• PSPNSV4-614: Feature: Implement API for AssetManagment
• PSPNSV4-613: Feature: extend I&M API so that a user is able to use I&M5 and modify its content as well

Changes:

• PSPNSV4-814: Replace error header "pns_error.h" with new naming convention matching file "pns_Results.h"
• PSPNSV4-793: Reject Get Parameter Service with unexpected length
• PSPNSV4-790: Update to DCERPC V5.3.0.2
• PSPNSV4-785: Ready bit not set when taglist contains invalid values or other startup problems occur
• PSPNSV4-778: Update PSPNCORE to V1.7.0.1
• PSPNSV4-772: [all firmwares]: reduce the amount of supported ARs to 2
• PSPNSV4-771: Drop support for I&M4 by default (can be enabled by application if required)
• PSPNSV4-767: harmonize public header file PNSIF_API.h with PNSv3 implementation
• PSPNSV4-746: Update external OSAL to V1.2.1.0
• PSPNSV4-719: Value 0 for usChannelErrType shall no longer be accepted while adding (Extended) Channel Diagnosis
• PSPNSV4-672: Drop support for HalfDuplex as well as 10MBit/s in Profinet switch
• PSPNSV4-660: update to rcX V2.1.11.11
• PSPNSV4-659: ResetToFactory with suboption "Reset communication parameter" shall no longer delete writable SNMP variables
• PSPNSV4-643: Adjust sysDescription for recommended value
• PSPNSV4-637: No Data Acknowledge for received alarms
• PSPNSV4-633: Update PSDCERPCV5 to V5.2.0.3
• PSPNSV4-627: Update PSLLDPV5 to V5.2.0.2
• PSPNSV4-626: harmonize firmware name for single port variant
• PSPNSV4-601: Update PSPNCORE to V1.7.0.0
• PSPNSV4-594: Update PSLWIP to V4.0.0.3

Bugs:

• PSPNSV4-817: AR Check Indication sometimes not generated
• PSPNSV4-813: Add PE Entity can be used multiple times on the same submodule
• PSPNSV4-811: in Read I&M indication the field abReserved is not initialized with 0
• PSPNSV4-810: [GSDML]: netX52 Single Port firmware related DeviceAccessPoint is missing for Firmware V4.4.0.0
• PSPNSV4-809: wrong Firmware Name given when reading Firmware Identification via DPM (limited firmware only)
• PSPNSV4-808: wrong Chip Type used in FileHeader
• PSPNSV4-794: Get Parameter Service returns uninitialized data for pdev diagnosis
• PSPNSV4-792: Unexpected behavior for I&M0, I&M5 and I&M Filter data when handled by application
• PSPNSV4-791: Limited firmware not behaving as expected
• PSPNSV4-776: Unexpected IRT AR abort when receiving wrong PTCP Sync frame
• PSPNSV4-774: multiple pull and plug of network cable may bring firmware in state that no cyclic communication can be established
• PSPNSV4-760: Invalid packet definition of PNS_IF_SET_SUBM_STATE_CNF_T and PNS_IF_GET_CONFIGURED_SUBM_REQ_T
• PSPNSV4-759: User Error Service Indication sent with non-zero status
• PSPNSV4-758: invalid value 0 for I&M-Flags is accepted for PNS_IF_SET_OEM_PRM_TYPE5
• PSPNSV4-744: sometimes unexpected behavior after plugging a wrong submoule at runtime
• PSPNSV4-743: No error reported when a none-existing diagnosis shall be removed with PNS_IF_REMOVE_DIAG_REQ
• PSPNSV4-739: Unfragmented acyclic service sometimes not working as expected if fragmented acyclic service was used upfront
• PSPNSV4-735: Firmware may crash or filesystem may get corrupted on SystemReset
• PSPNSV4-727: Sometimes host response packets ignored
• PSPNSV4-722: maximum possible size of ProcessAlarm can not be generated
• PSPNSV4-720: Some valid but unusual combinations of ChannelErrorType and ExtendedChannelErrorType are rejcted but should be accepted
• PSPNSV4-718: sometimes no LinkStatus Indication generated to application on register application sequence
• PSPNSV4-714: PNS_IF_GET_DIAGNOSIS_CNF does not return valid linedelay
• PSPNSV4-704: Alarm positively acknowledged even if application does not support PNS_IF_ALARM_IND
• PSPNSV4-695: LLDP Advertised Mau Types field wrong (certification issue)
• PSPNSV4-692: Valid IRT connection rejected with error "Invalid Sendclock Factor"
• PSPNSV4-680: Crash when read response length larger than internal buffer size
• PSPNSV4-667: Possible crash of netX52 firmwares
• PSPNSV4-654: Read InputDataObjectElement record using non owner AR delivers incorrect IOCS value
• PSPNSV4-651: Sometimes check indications are not reported as expected
• PSPNSV4-649: No ReleaseAlarm generated to IO Controller in case of SharedDevice (certification issue)
• PSPNSV4-645: Use FSPM profinet status codes on invalid Read/Write Record Service response packet from application
• PSPNSV4-636: [NXLFW]: generic tag to disable UART and USB diagnosis is missing
• PSPNSV4-635: Header file Sock_Results.h is not provided in distribution folder
• PSPNSV4-632: Wrong UDP source port for RPC Responses (certification issue)
• PSPNSV4-629: CMSU statemachine does not create static ARP Cache entry as expected
• PSPNSV4-623: Unexpected firmware behavior in case of advanced startup with FSU
• PSPNSV4-621: IOxS set to GOOD by default in case of correct module/submodule IDs but wrong IO data length
• PSPNSV4-611: Device not supporting I&M5 still include "OEM Device ID" suboption in the DCP device option list (certification issue)
• PSPNSV4-599: Manufacturer specific diagnosis are not included in response when reading diagnosis data objects
• PSPNSV4-598: Unexpected error code when plugging / configuring submodule
• PSPNSV4-595: Reading I&M fails if application handles I&M records
• PSPNSV4-531: No unused check indications on ar abort

Version V4.3.1.0

New Features:

• PSPNSV4-702: Feature: Add API to set some behavior related parameters via mailbox (formerly set via taglist)
• PSPNSV4-670: [NXLFW]: taglist shall allow more detailed modifications regarding memory quantity structure
• PSPNSV4-650: Feature: Add support for newly defined PNS_IF_Get_Parameter ParameterTypes
• PSPNSV4-618: Feature: Add firmware for new products netRAPID51-RE and netRAPID51-RE-IO
• PSPNSV4-617: Feature: Implement API for readout of Ethernet Parameters
• PSPNSV4-616: Feature: Implement API for PROFIenergy ASE
• PSPNSV4-615: Feature: Implement API for UserSpecific Alarms
• PSPNSV4-614: Feature: Implement API for AssetManagment
• PSPNSV4-613: Feature: extend I&M API so that a user is able to use I&M5 and modify its content as well

Changes:

• PSPNSV4-746: Update external OSAL to V1.2.1.0
• PSPNSV4-719: Value 0 for usChannelErrType shall no longer be accepted while adding (Extended) Channel Diagnosis
• PSPNSV4-672: Drop support for HalfDuplex as well as 10MBit/s in Profinet switch
• PSPNSV4-660: update to rcX V2.1.11.11
• PSPNSV4-659: ResetToFactory with suboption "Reset communication parameter" shall no longer delete writable SNMP variables
• PSPNSV4-643: Adjust sysDescription for recommended value
• PSPNSV4-637: No Data Acknowledge for received alarms
• PSPNSV4-633: Update PSDCERPCV5 to V5.2.0.3
• PSPNSV4-627: Update PSLLDPV5 to V5.2.0.2
• PSPNSV4-626: harmonize firmware name for single port variant
• PSPNSV4-601: Update PSPNCORE to V1.7.0.0
• PSPNSV4-594: Update PSLWIP to V4.0.0.3

Bugs:

• PSPNSV4-744: sometimes unexpected behavior after plugging a wrong submoule at runtime
• PSPNSV4-739: Unfragmented acyclic service sometimes not working as expected if fragmented acyclic service was used upfront
• PSPNSV4-735: Firmware may crash or filesystem may get corrupted on SystemReset
• PSPNSV4-727: Sometimes host response packets ignored
• PSPNSV4-722: maximum possible size of ProcessAlarm can not be generated
• PSPNSV4-718: sometimes no LinkStatus Indication generated to application on register application sequence
• PSPNSV4-714: PNS_IF_GET_DIAGNOSIS_CNF does not return valid linedelay
• PSPNSV4-704: Alarm positively acknowledged even if application does not support PNS_IF_ALARM_IND
• PSPNSV4-695: LLDP Advertised Mau Types field wrong (certification issue)
• PSPNSV4-692: Valid IRT connection rejected with error "Invalid Sendclock Factor"
• PSPNSV4-680: Crash when read response length larger than internal buffer size
• PSPNSV4-667: Possible crash of netX52 firmwares
• PSPNSV4-654: Read InputDataObjectElement record using non owner AR delivers incorrect IOCS value
• PSPNSV4-651: Sometimes check indications are not reported as expected
• PSPNSV4-649: No ReleaseAlarm generated to IO Controller in case of SharedDevice (certification issue)
• PSPNSV4-645: Use FSPM profinet status codes on invalid Read/Write Record Service response packet from application
• PSPNSV4-636: [NXLFW]: generic tag to disable UART and USB diagnosis is missing
• PSPNSV4-635: Header file Sock_Results.h is not provided in distribution folder
• PSPNSV4-632: Wrong UDP source port for RPC Responses (certification issue)
• PSPNSV4-629: CMSU statemachine does not create static ARP Cache entry as expected
• PSPNSV4-623: Unexpected firmware behavior in case of advanced startup with FSU
• PSPNSV4-621: IOxS set to GOOD by default in case of correct module/submodule IDs but wrong IO data length
• PSPNSV4-611: Device not supporting I&M5 still include "OEM Device ID" suboption in the DCP device option list (certification issue)
• PSPNSV4-599: Manufacturer specific diagnosis are not included in response when reading diagnosis data objects
• PSPNSV4-598: Unexpected error code when plugging / configuring submodule
• PSPNSV4-595: Reading I&M fails if application handles I&M records
• PSPNSV4-531: No unused check indications on ar abort

Version V4.3.0.10

Changes:

• PSPNSV4-837: Update lwIP component to V4.0.0.6

Bugs:

• PSPNSV4-857: PDRealData object misses PDPortStatistic block of interface submodule
• PSPNSV4-840: Packet Socket API crash on UDP traffic
• PSPNSV4-817: AR Check Indication sometimes not generated
• PSPNSV4-791: Limited firmware not behaving as expected

Version V4.3.0.9

Bugs:

• PSPNSV4-789: I&M5 Write request rejected with invalid error code

Version V4.3.0.8

Changes:

• PSPNSV4-777: Update PSPNCORE external to V1.5.0.5

Bugs:

• PSPNSV4-776: Unexpected IRT AR abort when receiving wrong PTCP Sync frame
• PSPNSV4-744: sometimes unexpected behavior after plugging a wrong submoule at runtime
• PSPNSV4-735: Firmware may crash or filesystem may get corrupted on SystemReset
• PSPNSV4-727: Sometimes host response packets ignored

Version V4.3.0.7

Changes:

• PSPNSV4-706: Update PSPNCORE to V1.5.0.4

Bugs:

• PSPNSV4-696: Update PSDRVETH to V1.4.0.1
• PSPNSV4-695: LLDP Advertised Mau Types field wrong (certification issue)
• PSPNSV4-680: Crash when read response length larger than internal buffer size
• PSPNSV4-667: Possible crash of netX52 firmwares
• PSPNSV4-654: Read InputDataObjectElement record using non owner AR delivers incorrect IOCS value

Version V4.3.0.6

Bugs:

• PSPNSV4-649: No ReleaseAlarm generated to IO Controller in case of SharedDevice (certification issue)

Version V4.3.0.5

Changes:

• PSPNSV4-637: No Data Acknowledge for received alarms

Version V4.3.0.4

Changes:

• PSPNSV4-633: Update PSDCERPCV5 to V5.2.0.3

Bugs:

• PSPNSV4-632: Wrong UDP source port for RPC Responses (certification issue)

Version V4.3.0.3

Changes:

• PSPNSV4-628: Update PSPNCORE to V1.5.0.3
• PSPNSV4-627: Update PSLLDPV5 to V5.2.0.2
• PSPNSV4-626: harmonize firmware name for single port variant

Version V4.3.0.2

Changes:

• PSPNSV4-624: update to PNCore V1.5.0.2

Bugs:

• PSPNSV4-623: Unexpected firmware behavior in case of advanced startup with FSU
• PSPNSV4-611: Device not supporting I&M5 still include "OEM Device ID" suboption in the DCP device option list (certification issue)

Version V4.3.0.1

Bugs:

• PSPNSV4-602: Update external PSLWIP to V4.0.0.4
• PSPNSV4-599: Manufacturer specific diagnosis are not included in response when reading diagnosis data objects
• PSPNSV4-598: Unexpected error code when plugging / configuring submodule
• PSPNSV4-531: No unused check indications on ar abort

Version V4.3.0.0

Changes:

• PSPNSV4-594: Update PSLWIP to V4.0.0.3
• PSPNSV4-584: Rework distribution folder structure
• PSPNSV4-553: Writing interface or port specific record objects outside the parameterization phase shall be rejected
• PSPNSV4-407: Update to PN Core V1.5.0.0

Bugs:

• PSPNSV4-595: Reading I&M fails if application handles I&M records
• PSPNSV4-592: Update to LWIP V4.0.0.2
• PSPNSV4-591: Unexpected Communication Errors under various conditions
• PSPNSV4-590: Update PSDCERPC to V5.2.0.2
• PSPNSV4-589: Wrong IO data transferred in DMA mode
• PSPNSV4-587: Update PSDCERPC to V5.2.0.1
• PSPNSV4-585: Upgrade device description files GSDML V2.33
• PSPNSV4-583: PNS_IF_RESET_FACTORY_SETTINGS_IND contains wrong usResetCode in case of "FactoryReset"
• PSPNSV4-582: Update to PSPNCORE V1.5.0.1
• PSPNSV4-577: No plug alarm when submodule plugged while AR startup
• PSPNSV4-576: Invalid behavior own submodule owner change or plug
• PSPNSV4-573: Occasionally no Connect response in case of Advanced Startupmode with FSU
• PSPNSV4-572: Connection via USB or UART unstable